Slightly more correct requirements#17
Merged
rafaelfranca merged 3 commits intorails:masterfrom Feb 15, 2019
deivid-rodriguez:better_requirements
Merged
Slightly more correct requirements#17rafaelfranca merged 3 commits intorails:masterfrom deivid-rodriguez:better_requirements
rafaelfranca merged 3 commits intorails:masterfrom
deivid-rodriguez:better_requirements
Conversation
| language: ruby | ||
| sudo: false | ||
| rvm: | ||
| - 2.2.4 |
Member
There was a problem hiding this comment.
Why ruby 2.2 support was removed? This gem still supports it.
Contributor
Author
There was a problem hiding this comment.
Sorry, will readd, was just quickly fixing CI.
To be explicitly about "allowing all prereleases".
Member
|
Thanks! |
Contributor
Author
|
Thank you! |
4 tasks
ghost
pushed a commit
to ruby/rubygems
that referenced
this pull request
Apr 15, 2019
2651: Restore transitiveness of version comparison r=bronzdoc a=deivid-rodriguez # Description: This is an alternative to #2597 fix to #2595. I strongly think this is the best way to fix this, even if it _could_ create some incompatibility with some gems relying on things like "~> 5.x" being lower than _all_ 5.0.0 prereleases. As explained in that discussion, the official way that's recommended in the docs to match all prereleases is "~> 5.a", because "a" is the first string in lexicographical order. I created PRs to the two gems I found relying on this: * rails/activemodel-serializers-xml#17 * rails/rails-controller-testing#45 I would consider this a bug fix and ship it normally on a bug fix release, but I can understand if others prefer a more conservative approach. # Tasks: - [x] Describe the problem / feature - [x] Write tests - [x] Write code to solve the problem - [ ] Get code review from coworkers / friends I will abide by the [code of conduct](https://github.com/rubygems/rubygems/blob/master/CODE_OF_CONDUCT.md). Co-authored-by: John Hawthorn <john@hawthorn.email>
pombredanne
pushed a commit
to aboutcode-org/univers
that referenced
this pull request
Dec 7, 2021
2651: Restore transitiveness of version comparison r=bronzdoc a=deivid-rodriguez # Description: This is an alternative to #2597 fix to #2595. I strongly think this is the best way to fix this, even if it _could_ create some incompatibility with some gems relying on things like "~> 5.x" being lower than _all_ 5.0.0 prereleases. As explained in that discussion, the official way that's recommended in the docs to match all prereleases is "~> 5.a", because "a" is the first string in lexicographical order. I created PRs to the two gems I found relying on this: * rails/activemodel-serializers-xml#17 * rails/rails-controller-testing#45 I would consider this a bug fix and ship it normally on a bug fix release, but I can understand if others prefer a more conservative approach. # Tasks: - [x] Describe the problem / feature - [x] Write tests - [x] Write code to solve the problem - [ ] Get code review from coworkers / friends I will abide by the [code of conduct](https://github.com/rubygems/rubygems/blob/master/CODE_OF_CONDUCT.md). Co-authored-by: John Hawthorn <john@hawthorn.email>
pombredanne
pushed a commit
to aboutcode-org/univers
that referenced
this pull request
Dec 7, 2021
2651: Restore transitiveness of version comparison r=bronzdoc a=deivid-rodriguez # Description: This is an alternative to #2597 fix to #2595. I strongly think this is the best way to fix this, even if it _could_ create some incompatibility with some gems relying on things like "~> 5.x" being lower than _all_ 5.0.0 prereleases. As explained in that discussion, the official way that's recommended in the docs to match all prereleases is "~> 5.a", because "a" is the first string in lexicographical order. I created PRs to the two gems I found relying on this: * rails/activemodel-serializers-xml#17 * rails/rails-controller-testing#45 I would consider this a bug fix and ship it normally on a bug fix release, but I can understand if others prefer a more conservative approach. # Tasks: - [x] Describe the problem / feature - [x] Write tests - [x] Write code to solve the problem - [ ] Get code review from coworkers / friends I will abide by the [code of conduct](https://github.com/rubygems/rubygems/blob/master/CODE_OF_CONDUCT.md). Co-authored-by: John Hawthorn <john@hawthorn.email>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This issue is just theoretical, just raising awareness of the problem. See ruby/rubygems#2597.